Fix Redis TLS configuration #137
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After an automatic maintenance task performed by Heroku, we started receiving several errors like:
RedisClient::CannotConnectError (SSL_connect returned=1 errno=0 peeraddr=52.18.173.200:21920 state=error: certificate verify failed (self signed certificate in certificate chain)Searching for solutions I found this from the Heroku Q&A.
With this PR, we configure Redis to accept messages using a TLS layer required in Redis 6+ in Heroku as described in the answer from the link above.